Repository navigation
Refuse a class over a type the catalog keeps out of the object layer - #71
Merged
estebanzimanyi merged 1 commit intoNov 16, 2026
Merged
Conversation
tools/objectgen.py stops before emitting the types layer when a class of the catalog's object model wraps a C type whose typeEncodings entry carries bindingScope: host for the time types a binding casts to its language's own, none for numeric, box2d and box3d, which no binding carries. MEOS-API refuses such a class when it derives the catalog (check_scope_classes); the generator reads the same mark, so a catalog from another derivation cannot hand C# one. Witness. Over the catalog of MobilityDB master af86409853 with a leaf Numeric under Value and its class over NumericData added to the object model, the shape the catalog held before numeric left binding scope, objectgen exits 1 with "classes over types out of the object layer: Numeric (NumericData, bindingScope none)"; over that catalog as derived it emits 154 classes and 5191 methods, 0 deferred, and the generated tree equals main's. Why. The owner ruled the time types host types and numeric, box2d and box3d out of binding scope; the catalog states the ruling once, in bindingScope, and each generator reads it rather than a list of its own. Measured over the catalog of MobilityDB master af86409853 and MEOS-API master ea8305118a: tools/codegen.py and tools/objectgen.py leave MEOS.NET/ and GAP-LEDGER.md byte-identical to main.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
tools/objectgen.py stops before emitting the types layer when a class of
the catalog's object model wraps a C type whose typeEncodings entry
carries bindingScope: host for the time types a binding casts to its
language's own, none for numeric, box2d and box3d, which no binding
carries. MEOS-API refuses such a class when it derives the catalog
(check_scope_classes); the generator reads the same mark, so a catalog
from another derivation cannot hand C# one.
Witness. Over the catalog of MobilityDB master af86409853 with a leaf
Numeric under Value and its class over NumericData added to the object
model, the shape the catalog held before numeric left binding scope,
objectgen exits 1 with "classes over types out of the object layer:
Numeric (NumericData, bindingScope none)"; over that catalog as derived
it emits 154 classes and 5191 methods, 0 deferred, and the generated
tree equals main's.
Why. The owner ruled the time types host types and numeric, box2d and
box3d out of binding scope; the catalog states the ruling once, in
bindingScope, and each generator reads it rather than a list of its own.
Measured over the catalog of MobilityDB master af86409853 and MEOS-API
master ea8305118a: tools/codegen.py and tools/objectgen.py leave
MEOS.NET/ and GAP-LEDGER.md byte-identical to main.